-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Escape angle brackets in configuration #9189
Conversation
Github markdown treats anything within angle brackets as an HTML tag. Due to this, data types such as `[array\<string>]` get rendered as `[array<string>]`. Many of the links are broken because of this because docusaurus doesn't read the hidden HTML tag.
Hi ayush000! Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file.In order for us to review and merge your code, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
Codecov Report
@@ Coverage Diff @@
## master #9189 +/- ##
==========================================
- Coverage 65.1% 65.09% -0.02%
==========================================
Files 278 278
Lines 11860 11860
Branches 2922 2921 -1
==========================================
- Hits 7722 7720 -2
- Misses 3510 3511 +1
- Partials 628 629 +1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done @SimenB . I wanted to ensure that the links generated by docusaurus on the Configuration page are working now. Is there a way to do that? |
You can run |
@SimenB Links are still not working. It seems to be bug in Docusaurus. I've filed a bug report on its repo. |
There's also a netlify deployment: https://deploy-preview-9189--jest-preview.netlify.com/ Thanks for reporting upstream! |
Docusaurus fixed the issue with link generation (PR here). I tested master branch of docusaurus locally. The config links are generated correctly in Table of Contents and in Navigation Sidebar. But I noticed that the Navigation sidebar is still showing I filed another issue on docusaurus's repo. |
Super cool, thanks for following up! |
To fix the Navigation sidebar rendering, the docusaurus team suggested replacing If docusaurus doesn't fix rendering of angle brackets in their next release, should I replace all angle brackets with |
Maybe better to close this PR. Its an upstream bug in Docusaurus which is fixed in next release. Someone should've pinged me 😆 |
Is it fixed in a release now? If so, maybe this pr can be changed to bumping the version instead? |
Wonderful, thank you! @ayush000 could you remove the md changes and update the version instead? 🙂 |
We still need to escape angle brackets. The links get fixed by docusaurus version bump, but it still doesn't render E.g.
|
Oh you are right. The bug in docusaurus is that the rendered markdown content, autogenerated toc and sidebar isn't consistent (but its consistent now) |
* master: chore: upgrade to fsevents 2 (jestjs#9215) docs: remove expect.assertions(1) in rejects example of Tutoria… (jestjs#9149) chore: bump to istanbul alphas (jestjs#9192) Fix typo in JestPlatform.md (jestjs#9212) jest-snapshot: Ignore indentation for most serialized objects (jestjs#9203) fix(jest-types): tighten Config types and set more defaults (jestjs#9200) jest-snapshot: Improve colors when snapshots are updatable (jestjs#9132) jest-snapshot: Omit irrelevant received properties when property matchers fail (jestjs#9198) chore: make changedFiles option optional in `shouldInstrument` (jestjs#9197) fix(pretty-format): correctly detect memo (jestjs#9196) chore: regenerate lockfiles in e2e tests (jestjs#9193) chore: bump handlebars
Thank you so much @ayush000, this is wonderful! |
@endiliey while you're here, the "read more" buttons on the blog are broken: https://jestjs.io/blog/. Known? |
interesting bug. can you help file an issue ? didnt know about it. We never really changed anything on that part though 😅. Is it working on 1.14 previously ? Its midnight here and am not within reach of pc I suspect css from facebook/docusaurus#1869 blocked that ?? cc @yangshun read more is broken :o |
I don't know when it broke, @pedrottimark alerted me to it now |
Please click on the post title for now. We'll push out a hotfix. |
@SimenB update to 1.14.2. Yeah its regression from 1.14.1. 1.14.0 was working fine. My suspicion was right, facebook/docusaurus#1869 broke it |
Updated in f4d0565, and I can confirm it fixes the issue. Thanks, as always, for the help! 🙂 |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
If you open Jest configuration page and click on moduleDirectories [array], the respective section doesn't open up.
This is because github markdown treats anything within angle brackets as an HTML tag. Due to this, data types such as
[array<string>]
get rendered as[array]
. Many of the links are broken because docusaurus doesn't read the hidden HTML tag.HTML tags can be escaped by prepending them with a backslash